Network node and method for handling measurements in a multi connectivity communication

ABSTRACT

A method performed by a network node for handling measurements in a multi connectivity communication between a User Equipment (UE), and multiple nodes is provided. The multiple nodes include a Master Node (MN), and one or more Secondary Nodes (SNs) in a wireless communication network. The network node is any one out of an MN and an SN. The network node sends at least one configuration to the UE. The at least one configuration comprises any one or more out of a path and a destination for sending a report from the UE to at least one out of the MN and the one or more SNs. The report is to include a result of a measurement according to a measurement configuration, configuring the UE to measure a respective frequency provided by at least one out of the MN and the one or more SNs for communication.

TECHNICAL FIELD

Embodiments herein relate to a network node and a method therein. Insome aspects, they relate to handling measurements in a multiconnectivity communication between a User Equipment (UE) and multiplenodes in a wireless communications network.

BACKGROUND

In a typical wireless communication network, wireless devices, alsoknown as wireless communication devices, mobile stations, stations (STA)and/or User Equipments (UE), communicate via a Local Area Network suchas a WiFi network or a Radio Access Network (RAN) to one or more corenetworks (CN). The RAN covers a geographical area which is divided intoservice areas or cell areas, which may also be referred to as a beam ora beam group, with each service area or cell area being served by aradio network node such as a radio access node e.g., a Wi-Fi accesspoint or a radio base station (RBS), which in some networks may also bedenoted, for example, a NodeB, eNodeB (eNB), or gNB as denoted in 5G. Aservice area or cell area is a geographical area where radio coverage isprovided by the radio network node. The radio network node communicatesover an air interface operating on radio frequencies with the wirelessdevice within range of the radio network node.

Specifications for the Evolved Packet System (EPS), also called a FourthGeneration (4G) network, have been completed within the 3rd GenerationPartnership Project (3GPP) and this work continues in the coming 3GPPreleases, for example to specify a Fifth Generation (5G) network alsoreferred to as 5G New Radio (NR). The EPS comprises the EvolvedUniversal Terrestrial Radio Access Network (E-UTRAN), also known as theLong Term Evolution (LTE) radio access network, and the Evolved PacketCore (EPC), also known as System Architecture Evolution (SAE) corenetwork. E-UTRAN/LTE is a variant of a 3GPP radio access network whereinthe radio network nodes are directly connected to the EPC core networkrather than to RNCs used in 3G networks. In general, in E-UTRAN/LTE thefunctions of a 3G RNC are distributed between the radio network nodes,e.g. eNodeBs in LTE, and the core network. As such, the RAN of an EPShas an essentially “flat” architecture comprising radio network nodesconnected directly to one or more core networks, i.e. they are notconnected to RNCs. To compensate for that, the E-UTRAN specificationdefines a direct interface between the radio network nodes, thisinterface being denoted the X2 interface.

Multi-antenna techniques can significantly increase the data rates andreliability of a wireless communication system. The performance is inparticular improved if both the transmitter and the receiver areequipped with multiple antennas, which results in a Multiple-InputMultiple-Output (MIMO) communication channel. Such systems and/orrelated techniques are commonly referred to as MIMO.

In addition to faster peak Internet connection speeds, 5G planning aimsat higher capacity than current 4G, allowing higher number of mobilebroadband users per area unit, and allowing consumption of higher orunlimited data quantities in gigabyte per month and user. This wouldmake it feasible for a large portion of the population to streamhigh-definition media many hours per day with their mobile devices, whenout of reach of Wi-Fi hotspots. 5G research and development also aims atimproved support of machine to machine communication, also known as theInternet of things, aiming at lower cost, lower battery consumption andlower latency than 4G equipment.

In 3GPP Dual-Connectivity (DC) has been specified, both for LTE andbetween LTE and NR. In DC two nodes involved, a Master Node (MN) or(MeNB) and a Secondary Node (SN) or (SeNB). Multi-Connectivity (MC) isthe case when there are more than two nodes involved.

3GPP Dual Connectivity

As mentioned above, DC is standardized for both LTE and E-UTRAN-NR DC(EN-DC).

LTE DC and EN-DC are design differently when it comes to which nodesthat control what. Basically, there are two options, a centralizedsolution like LTE-DC, and a decentralized solution, like EN-DC.

FIG. 1 shows a schematic control plane architecture looks like for LTEDC in a scenario with a UE, a Master Node (MN) and a Secondary Node(SN). FIG. 2 shows a schematic control plane architecture looks like forEN-DC in a scenario with a UE, an MN and an SN. The main difference hereis that in EN-DC, the SN has a separate Radio Resource Control (RRC)entity referred to as NR RRC. This means that the SN can control the UEalso; sometimes without the knowledge of the MN but often the SN need tocoordinate with the MN. In LTE-DC, the RRC decisions are always comingfrom the MN, from the MN to the UE. Note however, the SN still decidesthe configuration of the SN, since it is only the SN itself that hasknowledge of what kind of resources, capabilities etc. the SN have.

Below two different DC specifications and their RRC messages will bedescribed in more detail.

LTE DC

FIG. 3 illustrates an overview of the LTE-DC configurations. When anMeNB, referred to as MN in FIG. 3, decides to request 301 an SeNBaddition, the MeNB indicates 302 within Second Cell Group(SCG)-Configuration Information (ConfigInfo) See 3GPP TS 36.300 V15.2.0(2018-06), the Master Cell Group (MCG) configuration and the entire UEcapabilities for UE capability coordination as well as the latestmeasurement results for the SCG cell(s) requested to be added, see FIG.3. The SN responds 303 an acknowledgement with a SCG-Config and thelatest measConfig to the MeNB. If the MeNB accepts the SCG-Configconfigurations, it sends 304 this to the UE as well as the UEmeasurement configurations (MeasConfig) in theRRCConnectionReconfiguration message to the UE.

The MeNB cannot change the SCG Configuration from the SeNB, just acceptor reject. The reason for this is that the MeNB is not fully aware ofthe available resources and capabilities of the SeNB. Thus, if the MeNBmodifies the SCG-Configuration it can lead to a case that the UE willutilize incorrect resources. In practice, the measurement configurationis controlled by the MeNB. Note also that in LTE-DC centralized solutionthe UE's measurement report is sent 305 to the MeNB only.

EN-DC2

The second option is to use a decentralized option, which is used byEN-DC. This means that the SN can directly configure the UE withmeasurement.

In EN-DC, the main reason to have decentralized measurementconfigurations was latency requirements. Thus, by supporting a specialSignaling Radio Bearer, (SRB), referred to as SRB3, for the SN node ofNR, which allows the SN to configure the measurement separately withoutinvolving the MN, the SN can speed up the measurements and measurementconfigurations. The intention here is that the SRB3 using NR radio mayallow faster transmission than the corresponding LTE SRBs. Also, thebackhaul link, the so called X2 interface which may be exchanged with Xnin standalone NR use cases, which is used for communication between theMN and SN may be congested which may negatively affect both themeasurement reporting and new measurement configurations.

Thus, sending the UE measurement report directly to the concerned node,MN or SN, can speed up a necessary action such as e.g. switch a nodeand/or add a node. Another reason to have decentralized measurements isthat LTE and NR use slightly different RRC and different mobility, whichalso makes it convenient to split the responsibility.

The decentralized EN-DC solution option includes measurement capabilitycoordination. According to latest 3GPP agreement the SN shall inform theMN every time it changes which carrier frequencies the UE shall measureon. The measurement capability coordination is necessary to not exceedthe number of carriers the UE can measure, and also for the gapcoordination, this will be explained below. If MN and SN configure morecarriers than the UE can measure on, the UE probably will randomlyignore one or more carriers for measurements. In the worst case, theseignored carriers may be the most important carriers to measure on.

If the SN receives from the MN a new value for the maximum number offrequency layers or reporting configurations, and it has alreadyconfigured all the allowed measurements or reporting configurationsbased on the previous maximum values, it releases the required number ofmeasurements or reporting configurations to comply with the new limit.

Thus, it is important to coordinate the measured frequency carrierswhich is used to coordinate the measurement gaps. To understand why itis important to also coordinate the measurement gaps between MN and SN,it will be explained in more detail below how the measurements in EN-DCwork.

Regarding the EN-DC measurement configurations it should be noted thatan important difference compared to LTE-DC is that since the SN also canconfigure the UE's measurements, these are also transmitted to the SNvia the SRB3, if configured.

Measurement Gaps in EN-DC

EN-DC may use both “LTE frequencies” and very high 5G frequencies. 3GPPdistinguishes between FR1 frequency and FR2 frequency. FR1 frequency isbelow 6 GHz and FR2 is above 28 GHz. The reason this is done like thisis because of different UE capabilities. Some more advanced UEs canreceive data on FR1 and measure on FR2 simultaneously and vice versa,while some cannot measure on FR1 and receive data on FR2 at the sametime and vice versa.

To be able to measure on any of the frequencies FR1 and FR2, the UE mustbe configured with a so called gap, i.e. a certain time period when theUE does not receive any data on this frequency and can focus onmeasuring on other cells in this frequency range. If the UE can receivedata on FR1 and measure on FR2 simultaneously and vice versa, the gap iscalled “per-FR gap”. If a UE cannot measure on FR1 and receive data onFR2 simultaneously and vice versa, it is called “per-UE gap”. The mostefficient way is always to configure per-FR gap, because per-UE gap willinfluence the scheduling of all serving cells and consequently both FR1and FR2 data will be interrupted then, i.e. all data transmission willbe impacted for a short period for per-UE gap measurements.

RAN2 has agreed that the network can choose either per-UE gap or per-FRgap for a UE. As said earlier, both MN and SN can configure the UE withmeasurement gaps. Thus, some gap coordination is needed. This gapcoordination is a bit tricky.

In general, the MN configures the gap to the UE if the UE is per-UEcapable. Thus, the MN needs to know the SN frequencies in order tocalculate a suitable gap also for the SN, and then send this gapconfiguration to the SN. The SN can send the FR1 and/or FR2 frequenciesto the MN via Cell Group-Configuration.

If the UE is capable of per FR1 and/or FR2 gaps, it is decided that theMN configures the FR1 gaps and the SN configures the FR2 gaps. However,for the per FR1/FR2 gap case, the MN and SN need to coordinate the gaps,so they don't overlap.

For either per-UE gap or per-LTE/FR1 gap, the MN transmits the gappattern to the SN via CG-ConfigInfo. CG-ConfigInfo is the NR name of theSCG-Config in LTE.

Multi-Connectivity

The idea with Multi-Connectivity (MC) is that the UE can connect to morethan two nodes, i.e. more than one SN node. The benefits with MC aresimilar to DC, but MC allows even more new areas to be utilized, e.g.centralized scheduler, even more robust mobility etc.

For an MC solution with only one type of radio network nodes, e.g. NRbase stations, some of the above arguments to have a decentralizedsolution are not as strong anymore since all NR nodes should be equallycapable.

From a migration point of view, it is natural to continue using EN-DCprinciples also for MC, i.e. using a decentralized solution. Also, theremay still be cases when a decentralized measurement solution isbeneficial, e.g. when the network nodes have different capabilities e.g.700 MHz nodes vs. 28 GHz nodes.

SUMMARY

As part of developing embodiments herein, a problem was identified bythe inventors, and will first be discussed.

In case of NR-NR Dual Connectivity (NN-DC), both nodes can generate themeasurement configuration, so-called decentralized measurementconfiguration for e.g. at least the SN frequency. This configuration maybe conveyed to the UE via NR RRC Information Elements (IEs). In thiscase, content-wise the RRC reconfiguration message and specifically themeasurement configuration would look the same regardless of whogenerated the IEs since both nodes are NR. Since these IEs can be mappedto an RRC message carried over MN SRB regardless of which node generatedthe IE, i.e., the MN or SN, from the UE point of view, it is not visiblewho configured the measurement configuration. The wording mapped whenused herein means that the IE is included in the RRC message. In thiscase, it is not clear for the UE over which SRB the measurement reportshould be sent. If the measurement report is sent to the wrong node, itmay not be clear for the recipient node why it received the report.Also, if the received measurement report has a measurement Identity (ID)that was previously configured by the recipient node, there may be amisalignment in the configured and received measurement reports with aconsequent wrong network behavior. It has been noted that the problem iseven more severe when the scenario is an NR multi-connectivity scenario,i.e., one MN and more than one SN.

However, decentralized measurement configuration is complex tocoordinate, especially when the UEs measurement capabilities shall beutilized to the fully and also coordinate the measurement gaps. Then,the centralized approach where MN configures all the measurements may bepreferable, yet this approach also has some disadvantages such as thecase that all measurement reports are received by the MN. This may slowdown necessary mobility actions such as to switch and/or add node, newcells to measure on etc.

An object of embodiments herein is to improve the performance in awireless communications network using DC or MC.

According to an aspect of embodiments herein, the object is achieved bya method performed by a network node for handling measurements in amulti connectivity communication between a User Equipment, UE, andmultiple nodes. The multiple nodes comprise a Master Node, MN, and oneor more Secondary Nodes, SNs, in a wireless communication network. Thenetwork node is any one out of an MN 110 and an SN.

The network node sends 502 at least one configuration to the UE. The atleast one configuration comprises any one or more out of a path and adestination for sending a report from the UE to at least one out of theMN and the one or more SNs. The report is to comprise a result of ameasurement according to a measurement configuration, configuring the UEto measure a respective frequency provided by at least one out of the MNand the one or more SNs for communication.

According to another aspect of embodiments herein, the object isachieved by a network node for handling measurements in a multiconnectivity communication between a User Equipment, UE, and multiplenodes. The multiple nodes are adapted to comprise a Master Node, MN, andone or more Secondary Nodes, SNs, in a wireless communication network.The network node is adapted to be any one out of a MN and an SN. Thenetwork node is configured to send at least one configuration to the UE.The at least one configuration is adapted to comprise any one or moreout of: a path and a destination. The path and the destination are forsending a report from the UE 120 to at least one out of the MN and theone or more SNs. The report is adapted to comprise a result of ameasurement according to a measurement configuration. The measurementconfiguration configures the UE to measure a respective frequencyprovided by at least one out of: the MN and the one or more SNs forcommunication.

By including in a configuration, the path and the destination over whichthe UE should send the measurements reports to the respective MN and SN,any ambiguity in the measurement reporting is avoided. This results inan improved performance in the wireless communications network using DCor MC.

A further advantage of embodiments herein is that this enables a veryflexible way to configure the UE. For example, it enables a centralizedconfiguration so that the need for coordination of the measurements areminimized. Also, this enables a complete decentralized solution whichcan for example be useful when the X2/Xn link between the MN and SNs iscongested or if there is a need for the SN to act very fast based on UEmeasurements.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a schematic block diagram illustrating prior art.

FIG. 2 is a schematic block diagram illustrating prior art.

FIG. 3 is a schematic block diagram illustrating prior art.

FIG. 4 is a schematic block diagram illustrating embodiments of awireless communications network.

FIG. 5 is a flowchart depicting embodiments of a method in a networknode.

FIG. 6 is a flowchart depicting embodiments of a method in a networknode.

FIG. 7 is a flowchart depicting embodiments of a method in a networknode.

FIG. 8 is a schematic block diagram illustrating embodiments of awireless communications network.

FIG. 9 is a schematic block diagram illustrating embodiments of awireless communications network.

FIG. 10 is a schematic block diagram illustrating embodiments of awireless communications network.

FIG. 11 is a schematic block diagram illustrating embodiments of anetwork node.

FIG. 12 schematically illustrates a telecommunication network connectedvia an intermediate network to a host computer.

FIG. 13 is a generalized block diagram of a host computer communicatingvia a base station with a user equipment over a partially wirelessconnection.

FIGS. 14-17 are flowcharts illustrating methods implemented in acommunication system including a host computer, a base station and auser equipment.

DETAILED DESCRIPTION

According to some embodiments herein a measurement configuration of a UEmay be generated by either an MN or any of the SNs in a multiconnectivity communication. The measurement configuration comprises apath and/or destination information for reporting the measurementresults of the respective MN and SNs according to the respectivemeasurement configuration. The destination and/or path information maybe an SRB identity or similar identifier for the path and/ordestination. The SRB identity information may be included in ameasurement configuration information element or a measurement object inthe NR RRC specification and in the corresponding Abstract SyntaxNotation (ASN.1) of the NR RRC specification.

The SN measurement in the UE for the multi connectivity communicationmay be configured a) by the MN which may be referred to as centralized,or b) by any of the SNs which may be referred to as decentralized. Ineither case the measurement configuration may be sent via a final MN RRCmessage.

Embodiments herein relate to wireless communication networks in general.FIG. 4 is a schematic overview depicting a wireless communicationsnetwork 100. The radio communications network 100 comprises one or moreRANs 102 and one or more CNs 104. The radio communications network 100may use a number of different technologies, such as NB-IoT, CAT-M,Wi-Fi, eMTC, Long Term Evolution (LTE), LTE-Advanced, 5G, New Radio(NR), Wideband Code Division Multiple Access (WCDMA), Global System forMobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE),Worldwide Interoperability for Microwave Access (WiMax), or Ultra MobileBroadband (UMB), just to mention a few possible implementations.

Nodes operate in the radio communications network 100, such as a networknode 110, a network node 111, and a network node 112. The respectivenetwork nodes 110, 111, 112 provides radio coverage over a geographicalarea, which may also be referred to as a cell, a beam or a beam group ofthe same or different a Radio Access Technology (RAT), such as 5G, LTE,Wi-Fi, NB-IoT, CAT-M, Wi-Fi, eMTC or similar. The respective networknode 110, 111, 112 may e.g. be a transmission and reception point e.g. aradio access network node such as a Wireless Local Area Network (WLAN)access point or an Access Point Station (AP STA), an access controller,a base station, e.g. a radio base station such as a NodeB, an evolvedNode B (eNB, eNode B), a gNB, a base transceiver station, a radio remoteunit, an Access Point Base Station, a base station router, atransmission arrangement of a radio base station, a stand-alone accesspoint or any other network unit capable of communicating with a UEwithin the radio coverage area served by the respective network node110, 111, 112 depending e.g. on the radio access technology andterminology used. The respective network node 110, 111, 112 maycommunicate with a UE with Downlink (DL) transmissions to the UE andUplink (UL) transmissions from the UE.

In the wireless communication network 100, UEs e.g. a UE 120 operate.The UE may e.g. be a mobile station, a non-access point (non-AP) STA, aSTA, a user equipment and/or a wireless terminals, an NB-IoT device, aneMTC device and a CAT-M device, a WiFi device, an LTE device and an NRdevice communicate via one or more Access Networks (AN), e.g. RAN, toone or more core networks (CN). It should be understood by the skilledin the art that “UE” is a non-limiting term which means any terminal,wireless communication terminal, wireless device, Device to Device (D2D)terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay,mobile tablets or even a small base station communicating within a cell.

Methods according to embodiments herein may be performed by any of thenetwork nodes 110, 111, and 112. In an example scenario wherein the UE120 is using a multi-connectivity in a communication, the network node110 is a master node and may be referred to as the MN 110. Further, thenetwork nodes 111, and 112 are secondary nodes and may be referred to asthe SN 111 and the SN 112, or the SN 111, 112.

Methods for handling measurements in a multi connectivity communicationbetween the UE 120 multiple nodes in a wireless communications network100, are performed by any of the network nodes 110, 111, and 112. As analternative, a Distributed Node DN and functionality, e.g. comprised ina cloud 140 as shown in FIG. 4 may be used for performing or partlyperforming the methods.

To resolve the ambiguity in measurement reporting in case of NN-DC ormulti-connectivity, the UE 120 is configured over which path and/or towhich destination the UE should send a respective measurement report foreach measurement performed on the respective MN and SNs such as e.g.each object and each measurement event. In this case, an InformationElement (IE) configuring the measurement and measurement reportdestination may be generated by either MN 110 or SN 111, 112.

According to the ASN.1 terminology in NR RRC specification, see 3GPP TS38.331 or LTE RRC specification, see 3GPP TS 36.331, in ASN.1, everyfield encapsulates the corresponding information element. In case of ameasurement object:

A measurement object field (measObjec) in an IE is used for indicating aUE such as the UE 120 regarding measurement e.g., what frequency tomeasure according to the MeasObject IE description.

A measurement object IE (MeasObject) describes what information can beincluded in measurement object.

There is also measurement event configuration which is coupled with themeasObject fields so as to let the UE know when to send thesemeasurements carried out as measurement report to the network. All theseconfigurations are sent under an ASN.1 hierarchy of measurementconfiguration i.e., measConfig field includes measObject field and otherfields; and each field gets the corresponding IE filled with therespective configuration information according to the IE description.

To speed up mobility actions in some embodiments, e.g., any of handover,SN addition, change and modification, in case of NN-DC ormulti-connectivity, the UE 120 is configured over which path and/ordestination such as SRB it should send a measurement report for eachmeasurement object and possibly each measurement event. In this case, anIE configuring the measurement and measurement report destination isgenerated by the MN 110.

Decentralized Configuration

By including in the measurement configuration e.g. over which SRB the UE120 should send the measurements report, any ambiguity in themeasurement reporting in case of NN-DC is avoided. Also, an erroneousnetwork behavior is avoided in case the received measurement report wasintended for another network node.

Centralized Configuration

By decoupling the SN configuration and measurement configuration fromthe measurement reporting according to some embodiments herein, there isminimal need to coordinate the measurement frequencies and measurementgaps. Further on, since the SNs 111, 112 receives its own measurementreports, it is possible for the respective SN 111, 112 to act quickly onthese measurements if needed. Also, since the MN 110 may also receiveall the measurement reports it is possible for the MN 110 to make a morecentralized scheduler assuming a relatively fast BH for the X2/Xninterface is available.

Example embodiments of a flowchart depicting embodiments of a methodperformed by the network node 110, 111, 112 for handling measurements ina multi connectivity communication between the UE 120, and multiplenodes are depicted in FIG. 5 and will be described more in detail in thefollowing. The multiple nodes comprise the MN 110 and one or more SNs111, 112 in the wireless communication network 100. As mentioned abovethe MN 110 and the one or more SNs 111, 112 may use the same ordifferent radio access technology. The network node 110, 111, 112 is anyone out of: an MN 110 and an SN 111, 112.

It should be noted that the wording multi connectivity communicationwhen used herein means that the UE 120 is connected to one MN and one ormore SNs. This means that the wording multi connectivity comprises alsodual connectivity.

The method may comprise one or more of the following actions whichactions may be taken in any suitable order.

According to an example scenario the UE 120 is about to use multiconnectivity communication with multiple nodes in the wirelesscommunications network 100, and need to be configured.

Action 501.

In some embodiments, the network node 110, 111, 112 may obtain arespective configuration from each of the MN 110 and one or more SNs111, 112. Each configuration comprises any one or more out of a path andthe destination for sending a respective report from the UE 120 to eachone of the MN 110 and the one or more SNs 111, 112.

The respective report may in these embodiments comprise a result of arespective measurement according to the measurement configuration. Themeasurement configuration configures the UE 120 to measure a respectivefrequency provided by each respective MN 110 and one or more SNs 111,112 for communication.

This means that the network node 110, 111, 112, collects theconfigurations from all the nodes 110, 111, 112 in the communication.This is to send all configurations from the nodes in the communicationtogether in a message to the UE 120. The network node 110, 111, 112 mayobtains its own configuration and further collect configurations fromthe other nodes 110, 111, 112 in the communication. In one example thenetwork node 110, 111, 112 is the MN 110 which obtains its ownconfiguration and collects configurations from the SNs 111, 112 in thecommunication.

Action 502.

The network node 110, 111, 112 sends at least one configuration to theUE 120. The at least one configuration comprises any one or more out ofa path and a destination. The path and/or the destination are forsending a report from the UE 120 to at least one out of the MN 110 andthe one or more SNs 111, 112. The report is to comprise a result of ameasurement according to a measurement configuration. The measurementconfiguration configures the UE 120 to measure a respective frequencyprovided by at least one out of: the MN 110 and the one or more SNs 111,112 for communication. The frequency may comprise any one out of acarrier frequency, a frequency band and a part of a frequency band. Theat least one configuration may be sent to the UE 120 in an RRC message.

As mentioned above, in some embodiments the network node 110, 111, 112has obtained in Action 501 a respective configuration from each of theMN 110 and one or more SNs 111, 112. In these embodiments, the networknode 110, 111, 112 sends the at least one configuration to the UE 120 bysending to the UE 120 the respective obtained configuration for each oneout of the MN 110 and the one or more SNs 111, 112.

A path when used herein e.g. refers to information about which radiointerface(s) the UE 120 shall use for sending each respectivemeasurement report. Thus the respective path may e.g. comprise any oneor more out of an identifier for an SRB, an identifier for an MCG pathof the SRB, if it is a Split SRB, and an identifier for SCG path of theSRB, if it is a Split SRB. Thus, the path may e.g. be an identifier ofan SRB such as e.g., SRB1, SRB2 or SRB3 and/or an MCG/SCG path of theSRB if it is a Split SRB.

A destination when used herein refers to information about where the UE120 shall send each measurement report.

The respective destination may e.g. comprise any one or more out of: Anidentifier for an RRC entity, an identifier for a network node such ase.g. any of the MN 110 and the SNs 111, 112, and an identifier for acentral or distributed unit.

The at least one configuration may further comprise any one or more outof: The measurement configuration, and a measurement eventconfiguration. The measurement event configuration is for configuringthe UE 120 when to send the respective report comprising the result ofthe measurement, to the at least one out of: the MN 110 and the one ormore SNs 111, 112.

In some embodiments, the network node 110, 111, 112 is the MN 110. Inthese embodiments, the sending of at least one configuration to the UE120 comprises: Sending to the UE 120 the respective configuration foreach one out of the MN 110 and the one or more SNs 111, 112. In otherwords, in these embodiments, the at least one configuration comprisesmore than one configurations, i.e. a respective configuration for eachone out of the MN 110 and the one or more SNs 111, 112.

In these embodiments each respective configuration comprises any one ormore out of the path and the destination for sending a respective reportfrom the UE 120 to each one of the MN 110 and the one or more SNs 111,112. In other words, compared to the more general embodiments whereinthe report is sent to at least one out of the MN 110 and the one or moreSNs 111, 112, a respective report are in these centralized embodimentssent to from the UE 120 to each one of the MN 110 and the one or moreSNs 111, 112. The respective report is to comprise a result of arespective measurement according to the measurement configuration. Themeasurement configuration configures the UE 120 to measure a respectivefrequency provided by each respective MN 110 and one or more SNs 111,112 for communication.

The frequency may comprise any one out of a carrier frequency, afrequency band and a part of a frequency band.

The method described above will now be further explained andexemplified. It should be noted that the examples and embodimentsdescribed below and above may be used in any combination and in anysuitable way.

In some embodiments, it is assumed that each node such as e.g. the MN110 and the SNs 111, 112, configured within a multi-connectivityscenario adopts its own RRC entity where at least one of an RRCinformation element or an RRC message may be generated in each.

In some embodiments which may be referred to as a decentralizedconfiguration, both MN 110 and the SNs111, 112 generates its ownmeasurement configuration for e.g., the SN generates the measurementconfiguration to the UE 120 for the SN frequencies. This may be referredto as decentralized measurement configuration. An example of this isshown in FIG. 6, wherein the SN 111 is referred to as SN 1 and the SN112 is referred to as SN2. In this example, the MN 110 configures 601the SNs 111, 112 except for measurements. Instead each of the SNs 111,112 and also the MN 110 each configures the UE 120 themselves. Therespective MN 110 and the SNs 111, 112 each configures the UE 120 withpath and/or destination for the measurement reports such that the UE 120sends 602 a respective measurement report to the corresponding MN 110and the SNs 111, 112.

This configuration may be conveyed to the UE 120 via NR RRC IEs. In thiscase, content-wise the RRC reconfiguration message and specifically themeasConfig would look the same regardless of who generated the IEs whenboth the MN 110 and the SNs 111, 112 are NR. Furthermore, each of the MN110 and the SNs 111, 112 may include an SRB-Identity (ID) configurationin the measurement configuration IE and/or measurement configurationmessage, such as e.g., measConfig, by which the UE 120 should send themeasurement report.

In some examples, the measurement object(s) with the related measurementevent(s), are generated by the respective SN 111, 112 e.g., as ameasConfig IE and sent via inter-node RRC messages to the MN 110. Inthis case, the MN 110 generates the final measurement configurationincluding MN- and SN-generated measurement configurations. In thisembodiment, SRB-ID mapping may be done in measConfig IE or in themeasurement event or in measurement object.

MeasConfig IE when used herein means the information element describingthe measurement configuration for the UE 120.

Measurement event when used herein means to let the UE 120 know when tosend these measurements carried out as measurement report to thenetwork.

Measurement object when used herein means cells or specific frequenciesfor which specific measurement configuration parameters apply, e.g.specific offsets.

In some further examples, the same measurement object may be mapped withmultiple SRB-IDs in the measurement event level, i.e., in a ReportingConfigurations To Add and/or Modify (ReportConfigToAddMod) field, if themeasurement object is the same for the MN 1110 and the SN 111, 112.

In some other examples, the UE 120 reports the measurement reportdepending on the SRB-ID information given in the measurementconfiguration.

There may be more than one measurement configuration IE in the same RRCmessage: E.g., measConfig and measConfig-2 IEs carrying MN 110 and SN111, 12 measurement configurations for which the measurement report pathmay identified by the SRB-ID info included in each IE.

In some examples, SRB-ID info may be an optional field. In this case, ifthis info is not present, the measurement report is sent to the MN 110.

In some embodiments which may be referred to as centralizedconfiguration, the MN 110 may configure the UE 120 with pathand/destination for the MN 110 and the SNs 111, 112. An example of thisis shown in FIG. 7, wherein the SN 111 is referred to as SN 1 and the SN112 is referred to as SN2. In this example, the MN 110 configures 701the SNs 111, 112 including measurements. The MN 110 may send allmeasurement configurations relating to the MN 110 and the respective theSNs 111, 112 configuring the UE 120 with path and/or destination for themeasurement reports such that the UE 120 sends 702 a respectivemeasurement report to the corresponding MN 110 and the SNs 111, 112.

The MN 110 thus configures the UE 120 with the measurement report pathand/or destination e.g. for each measurement object, i.e. the UE 120measurement report may be sent to an MN RRC or an SN RRC entity via anMN SRB or SN SRB, respectively. The path and/or destination of eachmeasurement configuration may be marked by adding information and/or anidentifier of a higher layer on the SRB and/or target RRC i.e., by meansof SRB-ID within the measurement configuration such as MeasConfig IE.

In some examples, an RRC message may also mark a further path and/ordestination of each measurement configuration so as to configure whetherthe measurement report should be forwarded by the receiving network node120 to any other network node, and thus another RRC entity, than thepath and/or destination. E.g., to the MN 110 if the measurement reportpath and/or destination was the SN 111, 112. This is an advantage sinceit makes it easier to coordinate measurements and handling mobilitymanagement. In some examples, the forwarding node's RRC may adapt theforwarded message to the target node's RRC. In some other examples, theforwarding node's RRC may be embed in the same RRC message or IEs,without changing, in the inter-node RRC or inter-node message over anX2/Xn logical interface between the nodes.

In some examples, the path and/or destination may be identified by anSRB identifier or an RRC entity identifier within the multi-connectivityconfiguration. In one example, an SRB/RRC identifier, e.g., SRB-IDand/or RRC-ID, is an integer whose value is chosen from a range thatvaries from 1 to the maximum number of SRBs and/or RRC entitiesconfigured within the multi-connectivity configuration. Yet in anotherexample, the SRB and/or RRC identifier may be a sequence of fields thatbelongs to a given RRC entity e.g., Serving cell index, Logical channelidentity, etc. In another example, instead of a specific SRB and/or RRCidentifier, the identifier for a host may be used e.g., a Central nit(CU) identifier or a node and/or base station and/or gNB ID.

To be able to assess what configuration the measurement report iscoupled with, the configuring node's RRC entity may need to inform theother node's RRC entity that the UE 120 will report to about themeasurement configuration. In order to enable this, an inter-nodemessage over RRC or an inter-node message over X2/Xn logical interfacebetween the nodes such as the MN 110 and the SNs 111, 112 may be used.Accordingly, the inter-node RRC message may be embed in the fullmeasurement configuration or the part of the measurement configurationsuch as measurement ID, measurement triggers to the node(s) such as theMN 110 and the SNs 111, 112 that the UE 120 will report to.

In some of the centralized configuration embodiments, the MN 110 mayconfigure the UE 120 with measurements and gaps for the MN 110 and theSNs 111, 112.

RRC Message Implementation

The measurements configuration may be generated by the MN 110 or any ofthe SNs 111, 112, eNB and/or gNB via the RRC reconfiguration(RRCReconfiguration) message. An example of this is shown in FIG. 8,wherein the SN 111 is referred to as SN 1 and the SN 112 is referred toas SN2. In this example, the MN 110 configures 801 the SNs 111, 112including measurements. The MN 110 then configures 802 the UE 120 withall measurement configurations relating to the MN 110 and the respectivethe SNs 111, 112 by configuring the UE 120 with path and/or destinationfor the measurement reports such that the UE 120 sends 803 a respectivemeasurement report to the corresponding MN 110 and the SNs 111, 112.

In this case the UE 120 may be configured with the measConfig IE toperform intra and/or inter-frequency measurements and to which celland/or network node 110, 111, these should be reported. However, in thecurrent LTE and NR specification, the measurements report is sent to thenetwork node that has configured the UE. For this reason, an SRBidentity (SRB-ID) or similar identifier should be added to themeasConfig IE in order to enable the reporting to a different networknode.

Below an implementation example in the RRC specification is provided onhow to implement what has been described above regarding SRB-ID.

The example concerns a case where the SRB-ID is included in theMeasConfig IE that may be generated by the MN such as the MN 110 and SNsuch as any of the SNs 111, 112 and is used to specify measurements tobe performed by the UE such as the UE 120. In this example, the SRB-IDfield according to embodiments herein is underlined and is named assrbToReport.

MeasConfig information element:

-- ASN1START -- TAG-MEAS-CONFIG-START MeasConfig ::= SEQUENCE { measObjectToRemoveList   MeasObjectToRemoveList OPTIONAL,-- Need N measObjectToAddModList   MeasObjectToAddModList OPTIONAL,-- Need N reportConfigToRemoveList  ReportConfigToRemoveList OPTIONAL,-- Need N reportConfigToAddModList  ReportConfigToAddModList OPTIONAL,-- Need N measIdToRemoveList   MeasIdToRemoveList OPTIONAL,-- Need N measIdToAddModList   MeasIdToAddModList OPTIONAL,-- Need N s-MeasureConfig   CHOICE {   ssb-RSRP   RSRP-Range,   csi-RSRP  RSRP-Range  } OPTIONAL,-- Need M  quantityConfig  QuantityConfigOPTIONAL,-- Need M  measGapConfig   MeasGapConfig OPTIONAL,-- Need M measGapSharingConfig   MeasGapSharingConfig OPTIONAL,-- Need M  ···  [[ srbToReport          SEQUENCE (SIZE (1..3)) OF SRB-Identity OPTIONAL,-- Need M  ]]} MeasObjectToRemoveList ::=  SEQUENCE (SIZE (1..maxNrofObjectId)) OFMeasObjectId MeasIdToRemoveList ::=  SEQUENCE (SIZE (1..maxNrofMeasId))OF MeasId ReportConfigToRemoveList ::= SEQUENCE (SIZE(1..maxReportConfigId)) OF ReportConfigId -- TAG-MEAS-CONFIG-STOP --ASN1STOP

MeasConfig field descriptions measGapConfig Used to setup and releasemeasurement gaps in NR. measIdToAddModList List of measurementidentities to add and/or modify. measIdToRemoveList List of measurementidentities to remove. measObjectToAddModList List of measurement objectsto add and/or modify. measObjectToRemoveList List of measurement objectsto remove. reportConfigToAddModList List of measurement reportingconfigurations to add and/or modify reportConfigToRemoveList List ofmeasurement reporting configurations to remove. s-MeasureConfigThreshold for NR SpCell RSRP measurement controlling when the UE isrequired to perform measurements on non-serving cells. Choice ofssb-RSRP corresponds to cell RSRP based on SS/PBCH block and choice ofcsi-RSRP corresponds to cell RSRP of CSI-RS. The UE is only required toperform measurements on non- serving cells when the SpCell RSRP is belowthat threshold. MeasGapSharingConfig The IE MeasGapSharingConfigspecifies the measurement gap sharing scheme srbToReDort The list ofSRB-IDs over which the measurements report has to be sent.

FIG. 9 shows a flowchart of a simple example of the method in thenetwork node 110, 111, 112 according to embodiments herein. The MN 110receives 901 a measurement report from UE 120 and decides whether 902there is a new SN 111, 112 to add. When there is a new SN 111, 112 toadd, the MN 110 sends 903 a request to add to the new SN 111, 112 andmay reconfigure the UE 120 to add the new SN. The MN 110 or SN 111, 112configures 904 the UE 120 with the new SN frequencies to measure on. TheMN 110 or SN 111, 112 may send to and/or update 905 the UE 120 of thepath and/or destination of the new SN 111, 112 measurement reports.

FIG. 10 shows a flowchart of a simple example of the method in the UE120 according to embodiments herein. UE 120 sends 1001. a measurementreport to the MN 110. The UE 120 establishes 1002 whether it hasreceived a reconfiguration to add a new SN 111, 112. When the UE 120 hasreceived a reconfiguration to add a new SN 111, 112, the UE 120 receives1003 a measurement configurations for the new SN frequencies from MN 110or SN 111, 112. The UE 120 then receives 1004 the path and/ordestination for the new SN frequency measurement reports.

To perform the method actions for handling measurements in a multiconnectivity communication between the UE 120 and multiple nodes, thenetwork node 110, 111, 112, may comprise an arrangement depicted inFIGS. 11a and 11b . As mentioned above, the multiple nodes are adaptedto comprise the MN 110 and the one or more SNs 111, operable in thewireless communication network 100. The network node 111, 112 is adaptedto be any one out of the MN 110 and the SN 111, 112.

The network node 110, 111, 112 may comprise an Input and outputInterface configured to communicate with UEs such as the UE 120. Theinput and output interface may comprise a wireless receiver (not shown)and a wireless transmitter (not shown).

The network node 110, 111, 112 is configured to, e.g. by means of asending unit in the network node 112, send at least one configuration tothe UE 120. The at least one configuration is adapted to comprise anyone or more out of: a path and a destination for sending a report fromthe UE 120 to at least one out of the MN 110 and the one or more SNs111, 112, The report is adapted to comprise a result of a measurementaccording to a measurement configuration, configuring the UE 120 tomeasure a respective frequency provided by at least one out of: the MN110 and the one or more SNs 111, 112 for communication.

According to some embodiments, the network node 111, 112 is adapted tobe the MN 110, and the network node 110, 111, 112 may further beconfigured to e.g. by means of the sending unit 1110 in the network node112, send at least one configuration to the UE 120 by sending to the UE120 the respective configuration for each one out of the MN and the oneor more SNs 111, 112. In these embodiments, each respectiveconfiguration may be adapted to comprise any one or more out of: thepath and the destination for sending a respective report from the UE 120to each one of the MN 110 and the one or more SNs 111, 112. Therespective report is adapted to comprise a result of a respectivemeasurement according to the measurement configuration, configuring theUE 120 to measure a respective frequency provided by each respective MN110 and one or more SNs 111, 112 for communication.

The network node 110, 111, 112 may further being configured to e.g. bymeans of a obtaining unit 1120 in the network node 112, obtain arespective configuration from each of the MN 110 and one or more SNs111, 112. Each configuration may be adapted to comprise any one or moreout of: the path and the destination, for sending a respective reportfrom the UE 120 to each one of the MN 110 and the one or more SNs 111,112. The respective report is adapted to comprise a result of arespective measurement according to the measurement configuration,configuring the UE 120 to measure a respective frequency provided byeach respective MN 110 and one or more SNs 111, 112 for communication.In these embodiments, the network node 110, 111, 112 further isconfigured to send e.g. by means of the sending unit 1110 in the networknode 112, at least one configuration to the UE 120 by sending to the UE120 the respective obtained configuration for each one out of the MN 110and the one or more SNs 111, 112.

The respective destination may be adapted to comprise any one or moreout of: An identifier for an RRC entity, an identifier for a networknode, and an identifier for a central or distributed unit.

The respective path may be adapted to comprise any one or more out of:An identifier for an SRB, an identifier for a MCG path of the SRB if itis a Split SRB, and an identifier for SCG path of the SRB if it is aSplit SRB.

The at least one configuration may further be adapted to comprise anyone or more out of: The measurement configuration, and a measurementevent configuration, configuring the UE 120 when to send the respectivereport comprising the result of the measurement, to the at least one outof: the MN 110 and the one or more SNs 111, 112.

The at least one configuration may be adapted to be sent to the UE 120in an RRC message.

The frequency may be adapted to comprise any one out of: a carrierfrequency, a frequency band and a part of a frequency band.

The embodiments herein may be implemented through a respective processoror one or more processors, such as the processor 1130 of a processingcircuitry in the network node 110, 111, 112 depicted in FIG. 11a ,together with respective computer program code for performing thefunctions and actions of the embodiments herein. The program codementioned above may also be provided as a computer program product, forinstance in the form of a data carrier carrying computer program codefor performing the embodiments herein when being loaded into the networknode 110, 111, 112. One such carrier may be in the form of a CD ROMdisc. It is however feasible with other data carriers such as a memorystick. The computer program code may furthermore be provided as pureprogram code on a server and downloaded to the network node 110, 111,112.

The network node 110, 111, 112 may further comprise a memory 1140comprising one or more memory units. The memory 1140 comprisesinstructions executable by the processor in network node 110, 111, 112.The memory 1140 is arranged to be used to store e.g. data,configurations, and applications to perform the methods herein whenbeing executed in the network node 110, 111, 112.

In some embodiments, a respective computer program 1150 comprisesinstructions, which when executed by the respective at least oneprocessor 1130, cause the at least one processor of the network node110, 111, 112 to perform the actions above.

In some embodiments, a respective carrier 1160 comprises the respectivecomputer program 1150, wherein the carrier is one of an electronicsignal, an optical signal, an electromagnetic signal, a magnetic signal,an electric signal, a radio signal, a microwave signal, or acomputer-readable storage medium.

Those skilled in the art will appreciate that the sending unit 1110 andthe obtaining unit 1120 in the network node, 110, 111, 112, describedabove may refer to a combination of analog and digital circuits, and/orone or more processors configured with software and/or firmware, e.g.stored in the network node, 110, 111, 112, that when executed by therespective one or more processors such as the processors describedabove. One or more of these processors, as well as the other digitalhardware, may be included in a single Application-Specific IntegratedCircuitry ASIC), or several processors and various digital hardware maybe distributed among several separate components, whether individuallypackaged or assembled into a system-on-a-chip SoC).

Further Extensions and Variations

With reference to FIG. 12, in accordance with an embodiment, acommunication system includes a telecommunication network 3210 such asthe wireless communications network 100, e.g. an IoT network, or a WLAN,such as a 3GPP-type cellular network, which comprises an access network3211, such as a radio access network, and a core network 3214. Theaccess network 3211 comprises a plurality of base stations 3212 a, 3212b, 3212 c, such as the network node 110, 130, access nodes, AP STAs NBs,eNBs, gNBs or other types of wireless access points, each defining acorresponding coverage area 3213 a, 3213 b, 3213 c. Each base station3212 a, 3212 b, 3212 c is connectable to the core network 3214 over awired or wireless connection 3215. A first user equipment (UE) e.g. thewireless device 120 such as a Non-AP STA 3291 located in coverage area3213 c is configured to wirelessly connect to, or be paged by, thecorresponding base station 3212 c. A second UE 3292 e.g. the wirelessdevice 122 such as a Non-AP STA in coverage area 3213 a is wirelesslyconnectable to the corresponding base station 3212 a. While a pluralityof UEs 3291, 3292 are illustrated in this example, the disclosedembodiments are equally applicable to a situation where a sole UE is inthe coverage area or where a sole UE is connecting to the correspondingbase station 3212.

The telecommunication network 3210 is itself connected to a hostcomputer 3230, which may be embodied in the hardware and/or software ofa standalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. The host computer 3230 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider. Theconnections 3221, 3222 between the telecommunication network 3210 andthe host computer 3230 may extend directly from the core network 3214 tothe host computer or may go via an optional intermediate network 3220.The intermediate network may be one of, or a combination of more thanone of, a public, private or hosted network; the intermediate network3220, if any, may be a backbone network or the Internet; in particular,the intermediate network 3220 may comprise two or more sub-networks (notshown).

The communication system of FIG. 12 as a whole enables connectivitybetween one of the connected UEs 3291, 3292 and the host computer 3230.The connectivity may be described as an over-the-top (OTT) connection3250. The host computer 3230 and the connected UEs 3291, 3292 areconfigured to communicate data and/or signaling via the OTT connection3250, using the access network 3211, the core network 3214, anyintermediate network 3220 and possible further infrastructure (notshown) as intermediaries. The OTT connection 3250 may be transparent inthe sense that the participating communication devices through which theOTT connection 3250 passes are unaware of routing of uplink and downlinkcommunications. For example, a base station 3212 may not or need not beinformed about the past routing of an incoming downlink communicationwith data originating from a host computer 3230 to be forwarded (e.g.,handed over) to a connected UE 3291. Similarly, the base station 3212need not be aware of the future routing of an outgoing uplinkcommunication originating from the UE towards the host computer 3230.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 13. In a communicationsystem 3300, a host computer comprises hardware 3315 including acommunication interface 3316 configured to set up and maintain a wiredor wireless connection with an interface of a different communicationdevice of the communication system 3300. The host computer 3310 furthercomprises processing circuitry 3318, which may have storage and/orprocessing capabilities. In particular, the processing circuitry 3318may comprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. The host computer3310 further comprises software 3311, which is stored in or accessibleby the host computer 3310 and executable by the processing circuitry3318. The software includes a host application 3312. The hostapplication 3312 may be operable to provide a service to a remote user,such as a UE 3330 connecting via an OTT connection terminating at the UE3330 and the host computer 3310. In providing the service to the remoteuser, the host application 3312 may provide user data which istransmitted using the OTT connection 3350.

The communication system 3300 further includes a base station 3320provided in a telecommunication system and comprising hardware 3325enabling it to communicate with the host computer 3310 and with the UE3330. The hardware 3325 may include a communication interface 3326 forsetting up and maintaining a wired or wireless connection with aninterface of a different communication device of the communicationsystem 3300, as well as a radio interface 3327 for setting up andmaintaining at least a wireless connection 3370 with a UE 3330 locatedin a coverage area (not shown) served by the base station 3320. Thecommunication interface 3326 may be configured to facilitate aconnection 3360 to the host computer 3310. The connection 3360 may bedirect or it may pass through a core network (not shown in FIG. 13) ofthe telecommunication system and/or through one or more intermediatenetworks outside the telecommunication system. In the embodiment shown,the hardware 3325 of the base station 3320 further includes processingcircuitry 3328, which may comprise one or more programmable processors,application-specific integrated circuits, field programmable gate arraysor combinations of these (not shown) adapted to execute instructions.The base station 3320 further has software 3321 stored internally oraccessible via an external connection.

The communication system 3300 further includes the UE 3330 alreadyreferred to. Its hardware 3335 may include a radio interface 3337configured to set up and maintain a wireless connection 3370 with a basestation serving a coverage area in which the UE is currently located.The hardware 3335 of the UE 3330 further includes processing circuitry3338, which may comprise one or more programmable processors,application-specific integrated circuits, field programmable gate arraysor combinations of these (not shown) adapted to execute instructions.The UE 3330 further comprises software 3331, which is stored in oraccessible by the UE 3330 and executable by the processing circuitry3338. The software 3331 includes a client application 3332. The clientapplication 3332 may be operable to provide a service to a human ornon-human user via the UE 3330, with the support of the host computer3310. In the host computer 3310, an executing host application 3312 maycommunicate with the executing client application 3332 via the OTTconnection 3350 terminating at the UE 3330 and the host computer 3310.In providing the service to the user, the client application 3332 mayreceive request data from the host application 3312 and provide userdata in response to the request data. The OTT connection 3350 maytransfer both the request data and the user data. The client application3332 may interact with the user to generate the user data that itprovides.

It is noted that the host computer 3310, base station 3320 and UE 3330illustrated in FIG. 13 may be identical to the host computer 3230, oneof the base stations 3212 a, 3212 b, 3212 c and one of the UEs 3291,3292 of FIG. 14, respectively. This is to say, the inner workings ofthese entities may be as shown in FIG. 13 and independently, thesurrounding network topology may be that of FIG. 12.

In FIG. 13, the OTT connection 3350 has been drawn abstractly toillustrate the communication between the host computer 3310 and the useequipment via the base station 3320, without explicit reference to anyintermediary devices and the precise routing of messages via thesedevices. Network infrastructure may determine the routing, which it maybe configured to hide from the UE 3330 or from the service provideroperating the host computer 3310, or both. While the OTT connection 3350is active, the network infrastructure may further take decisions bywhich it dynamically changes the routing (e.g., on the basis of loadbalancing consideration or reconfiguration of the network).

The wireless connection 3370 between the UE 3330 and the base station isin accordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to the UE 3330 using the OTTconnection 3350, in which the wireless connection 3370 forms the lastsegment. More precisely, the teachings of these embodiments may improvethe applicable RAN effect: data rate, latency, power consumption, andthereby provide benefits such as corresponding effect on the OTTservice: e.g. reduced user waiting time, relaxed restriction on filesize, better responsiveness, extended battery lifetime.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring the OTT connection 3350 between the hostcomputer 3310 and UE 3330, in response to variations in the measurementresults. The measurement procedure and/or the network functionality forreconfiguring the OTT connection 3350 may be implemented in the software3311 of the host computer 3310 or in the software 3331 of the UE 3330,or both. In embodiments, sensors (not shown) may be deployed in or inassociation with communication devices through which the OTT connection3350 passes; the sensors may participate in the measurement procedure bysupplying values of the monitored quantities exemplified above, orsupplying values of other physical quantities from which software 3311,3331 may compute or estimate the monitored quantities. The reconfiguringof the OTT connection 3350 may include message format, retransmissionsettings, preferred routing etc.; the reconfiguring need not affect thebase station 3320, and it may be unknown or imperceptible to the basestation 3320. Such procedures and functionalities may be known andpracticed in the art. In certain embodiments, measurements may involveproprietary UE signaling facilitating the host computer's 3310measurements of throughput, propagation times, latency and the like. Themeasurements may be implemented in that the software 3311, 3331 causesmessages to be transmitted, in particular empty or ‘dummy’ messages,using the OTT connection 3350 while it monitors propagation times,errors etc.

FIG. 14 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station such asthe network node 110, and a UE such as the wireless device 120, whichmay be those described with reference to FIG. 12 and FIG. 13. Forsimplicity of the present disclosure, only drawing references to FIG. 14will be included in this section. In a first action 3410 of the method,the host computer provides user data. In an optional sub action 3411 ofthe first action 3410, the host computer provides the user data byexecuting a host application. In a second action 3420, the host computerinitiates a transmission carrying the user data to the UE. In anoptional third action 3430, the base station transmits to the UE theuser data which was carried in the transmission that the host computerinitiated, in accordance with the teachings of the embodiments describedthroughout this disclosure. In an optional fourth action 3440, the UEexecutes a client application associated with the host applicationexecuted by the host computer.

FIG. 15 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station such as anAP STA, and a UE such as a Non-AP STA which may be those described withreference to FIG. 12 and FIG. 13. For simplicity of the presentdisclosure, only drawing references to FIG. 15 will be included in thissection. In a first action 3510 of the method, the host computerprovides user data. In an optional sub action (not shown) the hostcomputer provides the user data by executing a host application. In asecond action 3520, the host computer initiates a transmission carryingthe user data to the UE. The transmission may pass via the base station,in accordance with the teachings of the embodiments described throughoutthis disclosure. In an optional third action 3530, the UE receives theuser data carried in the transmission.

FIG. 16 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station such as aAP STA, and a UE such as a Non-AP STA which may be those described withreference to FIG. 12 and FIG. 13. For simplicity of the presentdisclosure, only drawing references to FIG. 16 will be included in thissection. In an optional first action 3610 of the method, the UE receivesinput data provided by the host computer. Additionally or alternatively,in an optional second action 3620, the UE provides user data. In anoptional sub action 3621 of the second action 3620, the UE provides theuser data by executing a client application. In a further optional subaction 3611 of the first action 3610, the UE executes a clientapplication which provides the user data in reaction to the receivedinput data provided by the host computer. In providing the user data,the executed client application may further consider user input receivedfrom the user. Regardless of the specific manner in which the user datawas provided, the UE initiates, in an optional third sub action 3630,transmission of the user data to the host computer. In a fourth action3640 of the method, the host computer receives the user data transmittedfrom the UE, in accordance with the teachings of the embodimentsdescribed throughout this disclosure.

FIG. 17 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station such as anAP STA, and a UE such as a Non-AP STA which may be those described withreference to FIG. 12 and FIG. 13. For simplicity of the presentdisclosure, only drawing references to FIG. 17 will be included in thissection. In an optional first action 3710 of the method, in accordancewith the teachings of the embodiments described throughout thisdisclosure, the base station receives user data from the UE. In anoptional second action 3720, the base station initiates transmission ofthe received user data to the host computer. In a third action 3730, thehost computer receives the user data carried in the transmissioninitiated by the base station.

When using the word “comprise” or “comprising” it shall be interpretedas non-limiting, i.e. meaning “consist at least of”.

The embodiments herein are not limited to the above described preferredembodiments. Various alternatives, modifications and equivalents may beused.

1. A method performed by a network node for handling measurements in amulti connectivity communication between a User Equipment, UE, andmultiple nodes, the multiple nodes having a Master Node, MN, and one ormore Secondary Nodes, SNs, in a wireless communication network, thenetwork node being any one out of: an MN and an SN, the methodcomprising: sending at least one configuration to the UE, which at leastone configuration comprises: any one or more out of: a path and adestination for sending a report from the UE to at least one out of: theMN and the one or more SNs, which report is to comprise a result of ameasurement according to a measurement configuration, configuring the UEto measure a respective frequency provided by at least one out of: theMN and the one or more SNs for communication.
 2. The method according toclaim 1, wherein the network node is the MN, and wherein sending atleast one configuration to the UE comprises: sending to the UE therespective configuration for each one out of the MN and the one or moreSNs, wherein each respective configuration comprises: any one or moreout of: the path and the destination for sending a respective reportfrom the UE to each one of the MN and the one or more SNs, whichrespective report is to comprise a result of a respective measurementaccording to the measurement configuration, configuring the UE tomeasure a respective frequency provided by each respective MN and one ormore SNs for communication.
 3. The method according to claim 1, furthercomprising: obtaining a respective configuration from each of the MN andone or more SNs, wherein each configuration comprises: any one or moreout of: the path and the destination for sending a respective reportfrom the UE to each one of the MN and the one or more SNs, whichrespective report is to comprise a result of a respective measurementaccording to the measurement configuration, configuring the UE tomeasure a respective frequency provided by each respective MN and one ormore SNs for communication, and wherein sending at least oneconfiguration to the UE comprises: sending to the UE the respectiveobtained configuration for each one out of the MN and the one or moreSNs.
 4. The method according to claim 1, wherein the respectivedestination comprises any one or more out of: an identifier for an RRCentity, an identifier for a network node, and an identifier for acentral or distributed unit.
 5. The method according to claim 1, whereinthe respective path comprises any one or more out of: an identifier fora Signaling Radio Bearer, SRB, an identifier for a Master Cell Group,MCG, path of the SRB, if it is a Split SRB, and an identifier for SecondCell Group, SCG path of the SRB, if it is a Split SRB.
 6. The methodaccording to claim 1, wherein the at least one configuration furthercomprises any one or more out of: the measurement configuration, and ameasurement event configuration, configuring the UE when to send therespective report comprising the result of the measurement, to the atleast one out of: the MN and the one or more SNs.
 7. The methodaccording to claim 1, wherein the at least one configuration is sent tothe UE in a Radio Resource Control, RRC, message.
 8. The methodaccording to claim 1, wherein the frequency comprises any one out of: acarrier frequency, a frequency band and a part of a frequency band.
 9. Acomputer storage medium storing a computer program comprisinginstructions, which when executed by a processor, cause the processor toperform a method for a network node for handling measurements in a multiconnectivity communication between a User Equipment, UE, and multiplenodes, the multiple nodes having a Master Node, MN, and one or moreSecondary Nodes, SNs, in a wireless communication network, the networknode being any one out of: an MN and an SN, the method comprising:sending at least one configuration to the UE, which at least oneconfiguration comprises: any one or more out of: a path and adestination for sending a report from the UE to at least one out of: theMN and the one or more SNs, which report is to comprise a result of ameasurement according to a measurement configuration, configuring the UEto measure a respective frequency provided by at least one out of: theMN and the one or more SNs for communication.
 10. (canceled)
 11. Anetwork node for handling measurements in a multi connectivitycommunication between a User Equipment, UE, and multiple nodes, themultiple nodes comprising a Master Node, MN, and one or more SecondaryNodes, SNs, in a wireless communication network, the network node beingconfigured to be any one out of: a MN and an SN, the network nodefurther being configured to: send at least one configuration to the UE,which at least one configuration comprises: any one or more out of: apath and a destination for sending a report from the UE to at least oneout of: the MN and the one or more SNs, which report is adapted tocomprise a result of a measurement according to a measurementconfiguration, configuring the UE to measure a respective frequencyprovided by at least one out of: the MN and the one or more SNs forcommunication.
 12. The network node according to claim 11, wherein thenetwork node is configured to be the MN, and wherein the network nodefurther is configured to send at least one configuration to the UE bysending to the UE the respective configuration for each one out of theMN and the one or more SNs, wherein each respective configurationcomprises: any one or more out of: the path and the destination forsending a respective report from the UE to each one of the MN and theone or more SNs, which respective report is adapted to comprise a resultof a respective measurement according to the measurement configuration,configuring the UE to measure a respective frequency provided by eachrespective MN and one or more SNs for communication.
 13. The networknode according to claim 11, further being configured to: obtain arespective configuration from each of the MN and one or more SNs,wherein each configuration comprises: any one or more out of: the pathand the destination for sending a respective report from the UE to eachone of the MN and the one or more SNs, which respective report isadapted to comprise a result of a respective measurement according tothe measurement configuration, configuring the UE to measure arespective frequency provided by each respective MN and one or more SNsfor communication, and wherein the network node further is configured tosend at least one obtained configuration to the UE by sending to the UEthe respective configuration for each one out of the MN and the one ormore SNs.
 14. The network node according to claim 11, wherein therespective destination is comprises any one or more out of: anidentifier for an RRC entity, an identifier for a network node, and anidentifier for a central or distributed unit.
 15. The network nodeaccording to claim 11, wherein the respective path comprises any one ormore out of: an identifier for a Signaling Radio Bearer, SRB, anidentifier for a Master Cell Group, MCG, path of the SRB, if it is aSplit SRB, and an identifier for Second Cell Group, SCG path of the SRB,if it is a Split SRB.
 16. The network node according to claim 11,wherein the at least one configuration further comprises any one or moreout of: the measurement configuration, and a measurement eventconfiguration, configuring the UE when to send the respective reportcomprising the result of the measurement, to the at least one out of:the MN and the one or more SNs.
 17. The network node according to claim11, wherein the at least one configuration is configured to be sent tothe UE in a Radio Resource Control, RRC, message.
 18. The network nodeaccording to claim 11, wherein the frequency comprises any one out of: acarrier frequency, a frequency band and a part of a frequency band. 19.The method according to claim 2, wherein the respective destinationcomprises any one or more out of: an identifier for an RRC entity, anidentifier for a network node, and an identifier for a central ordistributed unit.
 20. The method according to claim 2, wherein therespective path comprises any one or more out of: an identifier for aSignaling Radio Bearer, SRB, an identifier for a Master Cell Group, MCG,path of the SRB, if it is a Split SRB, and an identifier for Second CellGroup, SCG path of the SRB, if it is a Split SRB.
 21. The methodaccording to claim 2, wherein the at least one configuration furthercomprises any one or more out of: the measurement configuration, and ameasurement event configuration, configuring the UE when to send therespective report comprising the result of the measurement, to the atleast one out of: the MN and the one or more SNs.